• feat: add Stainless SDK config and misc cleanups #132
• feat: rename Error to GridError and add additionalProperties to error schemas #131
• feat: add Customer API discriminators and consolidate customer changes #130
• feat: add Quote/Transaction discriminators and remove inline examples #129
• feat: add isPlatformAccount to PaymentInstructions and remove PaymentAccountOrWalletInfo refs #128
• feat: rename accounts to data in list external accounts response #127 👈 (View in Graphite)
• feat: convert single-value enums to const for base types #126
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Greptile Overview

Greptile Summary

This PR standardizes the response format for the GET /platform/external-accounts endpoint by renaming the accounts property to data. This change brings consistency with all other list endpoints in the API (customers, internal accounts, transactions, quotes, tokens) which already use data as the top-level array property.

Key changes:

• Updated OpenAPI schema in source file openapi/paths/platform/platform_external_accounts.yaml
• Regenerated bundled files openapi.yaml and mintlify/openapi.yaml to reflect the change
• Both required property name and property definition changed from accounts to data

Breaking change consideration:
This is a breaking API change that will require client code updates. Any consumers of this endpoint currently accessing response.accounts will need to update to response.data. The PR description mentions this in the testing section but could be more explicit about the breaking nature of this change.

Confidence Score: 4/5

• This PR is safe to merge from a code quality perspective, but introduces a breaking API change that requires coordination
• The schema changes are technically correct and bring consistency to the API. The OpenAPI specification is properly updated in both source and generated files. However, this is a breaking change that will impact existing API consumers, requiring them to update their integration code from response.accounts to response.data. The score is 4/5 rather than 5/5 because the breaking nature warrants careful deployment planning and client notification.
• No files require special attention - all changes are straightforward schema updates

sequenceDiagram
    participant Client
    participant API as Grid API
    participant Schema as OpenAPI Schema
    
    Note over Client,Schema: Before Change (Inconsistent)
    Client->>API: GET /platform/external-accounts
    API->>Schema: Validate response schema
    Note over Schema: Response uses "accounts" property
    Schema-->>API: Schema validation
    API-->>Client: { "accounts": [...] }
    Note over Client: Inconsistent with other endpoints
    
    Note over Client,Schema: After Change (Consistent)
    Client->>API: GET /platform/external-accounts
    API->>Schema: Validate response schema
    Note over Schema: Response uses "data" property
    Schema-->>API: Schema validation
    API-->>Client: { "data": [...] }
    Note over Client: Now consistent with all other list endpoints